Inference of an Intended Primary Display of a Hinged Mobile Device

ABSTRACT

Techniques for inference of an intended primary display of a hinged mobile device are described. Generally, the techniques described herein improve a user experience when the user interacts with the device, such as to change the posture of the device. For example, the techniques described herein detect physical movement of a first and/or second display portion of the device. In implementations, the physical movement is recognized as a device gesture to indicate which of the display portions is intended to be used as the primary display. Then, a determination is made that the first display portion is intended to be used as the primary display based on the device gesture. Based on the determination, the primary display is initiated via the first display portion.

BACKGROUND

Mobile devices provide today's user with a variety of differentfunctionalities, and in many instances allow the user to directlyinteract with objects displayed via touch-sensitive display devices.Devices having multiple display surfaces connected by a hinge, however,introduce complexities that are typically not resolved usingconventional gesture input modalities. Such a device can include twoportions of the device that each include a display screen and which areconnected by a physical hinge that can be manipulated by the user. Inthe context of a book or journal, for example, a user can view two pagesin a way that resembles a paper book or a notebook.

Because of the physical connection between the two portions of thedevice, the device can be positioned in a variety of different postures,some of which include one display facing the user and the other displayfacing away from the user. In some instances, the user may wish tointeract primarily with one display as opposed to the other. Bydisplaying content on both displays and/or on a secondary display,however, processing bandwidth is consumed as well as valuable batterylife. This can detract from user enjoyment and lead to user frustrationwhen using these types of devices.

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Techniques for inference of an intended primary display of a hingedmobile device are described. Generally, the techniques described hereinadapt a user experience when the user interacts with the device, such asto change the posture (e.g., position and orientation in space) of thedevice. For example, the techniques described herein detect physicalmovement of a first and/or a second display portion of the device. Inimplementations, the physical movement is recognized as a device gestureto indicate which of the display portions is intended to be used as theprimary display. Further, a determination is made that the first displayportion is intended to be used as the primary display based on thedevice gesture. Based on the determination, the primary display isinitiated via the first display portion.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different instances in thedescription and the figures may indicate similar or identical items.Entities represented in the figures may be indicative of one or moreentities and thus reference may be made interchangeably to single orplural forms of the entities in the discussion.

FIG. 1 is an illustration of an environment in an example implementationthat is operable to employ the techniques described herein in accordancewith one or more embodiments.

FIG. 2 depicts an example implementation scenario for interactionbetween various components of the client device from FIG. 1.

FIG. 3 depicts example implementation scenarios of devices that includefunctionality for inference of an intended primary display in accordancewith one or more embodiments.

FIG. 4 depicts example implementation scenarios for postures of a hingeddevice in accordance with one or more embodiments.

FIG. 5 depicts an example implementation scenario for inference of anintended primary display of a hinged mobile device in accordance withone or more embodiments.

FIG. 6 depicts an example implementation scenario which represents aflip gesture to switch displays in accordance with one or moreembodiments.

FIG. 7 depicts an example implementation scenario for inference of anintended primary display of a hinged mobile device in accordance withone or more embodiments.

FIG. 8 depicts an example implementation scenario for inference of anintended primary display of a hinged mobile device in accordance withone or more embodiments.

FIG. 9 depicts an example implementation scenario for inference of anintended primary display of a hinged mobile device in accordance withone or more embodiments.

FIG. 10 is a flow diagram that describes steps in a method for inferringan intended primary display of a hinged mobile device in accordance withone or more implementations.

FIG. 11 is a flow diagram that describes steps in a method for inferringan intended primary display of a hinged mobile device in accordance withone or more implementations.

FIG. 12 illustrates an example system including various components of anexample device that can be implemented as any type of computing deviceas described with reference to FIGS. 1-11 to implement embodiments ofthe techniques described herein.

DETAILED DESCRIPTION

Overview

Techniques for inference of an intended primary display of a hingedmobile device are described. A hinged mobile device, for example,represents a device with two (or more) displays attached to one anothervia a hinge portion. Generally, the techniques described herein improvea user experience when the user interacts with the device, such as tochange the posture of the device. For example, the techniques describedherein utilize a variety of sensor signals to infer which display of thedevice the user intends to use as a primary display. In implementations,the user manipulates the device by bending the hinge or physicallymoving the device to face a different direction. Sensors can be used todetect which display is facing the user and/or which display has theleast relative physical displacement in order to infer the user'sintended primary display. This inference can be verified usingadditional data, such as how the user is holding the device, a contextassociated with the user or the device, behavioral patterns, hand sizeand shape, sound data, and so on.

Using the sensor signals, the primary display can be selected and insome instances, a secondary display can be turned off or transitionedinto a sleep mode to conserve battery life and processing power. Inanother implementation, touch input to the secondary display can betreated differently than touch input to the primary display, such as byproviding particular user interface controls to a primary user via theprimary display that are not provided via a secondary display to anotheruser. Further discussion of these and other aspects are provided belowin more detail.

In the following discussion, an example environment is first describedthat is operable to employ techniques described herein. Next, a sectionentitled “Example Implementation Scenarios” describes some exampleimplementation scenarios in accordance with one or more embodiments.Following this, a section entitled “Example Procedures” describes someexample procedures in accordance with one or more embodiments. Finally,a section entitled “Example System and Device” describes an examplesystem and device that are operable to employ techniques discussedherein in accordance with one or more embodiments.

Having presented an overview of example implementations in accordancewith one or more embodiments, consider now an example environment inwhich example implementations may by employed.

Example Environment

FIG. 1 is an illustration of an environment 100 in an exampleimplementation that is operable to employ techniques for inference of anintended primary display of a hinged mobile device discussed herein.Environment 100 includes a client device 102 which can be configured formobile use, such as a mobile phone, a tablet computer, a wearabledevice, a handheld gaming device, a media player, and so on. The clientdevice 102 includes a display device 104 and a display device 106 thatare connected to one another by a hinge 108. The display device 104includes a touch surface 110, and the display device 106 includes atouch surface 112. The client device 102 also includes an input module114 configured to process input received via one of the touch surfaces110, 112, via the hinge 108, and/or via one or more other sensors 132.

The hinge 108 is configured to rotationally move about a longitudinalaxis 116 of the hinge 108 to allow an angle between the display devices104, 106 to change. In this way, the hinge 108 allows the displaydevices 104, 106 to be connected to one another yet be oriented atdifferent angles and/or planar orientations relative to each other. Inat least some implementations, the touch surfaces 110, 112 may representdifferent portions of a single integrated and continuous display surfacethat can be bent along the hinge 108. Thus, the hinge 108 may representa separate component that hingeably attaches the two separate touchsurfaces 110, 112, or the hinge 108 may represent a portion of a singleintegrated display surface that includes the touch surfaces 110, 112 andabout which the touch surfaces 110, 112 can bend.

While implementations presented herein are discussed in the context of amobile device, it is to be appreciated that various other types and formfactors of devices may be utilized in accordance with the claimedimplementations. Thus, the client device 102 may range from fullresource devices with substantial memory and processor resources, to alow-resource device with limited memory and/or processing resources. Anexample implementation of the client device 102 is discussed below withreference to FIG. 12.

The client device 102 includes a variety of different functionalitiesthat enable various activities and tasks to be performed. For instance,the client device 102 includes an operating system 118, applications120, and a communication module 122. Generally, the operating system 118is representative of functionality for abstracting various systemcomponents of the client device 102, such as hardware, kernel-levelmodules and services, and so forth. The operating system 118, forinstance, can abstract various components (e.g., hardware, software, andfirmware) of the client device 102 to enable interaction between thecomponents and applications running on the client device 102.

The applications 120 are representative of functionality for performingdifferent tasks via the client device 102. In one particularimplementation, the applications 120 represent a web browser, webplatform, or other application that can be leveraged to browse websitesover a network.

The communication module 122 is representative of functionality forenabling the client device 102 to communicate over wired and/or wirelessconnections. For instance, the communication module 122 representshardware and logic for communicating data via a variety of differentwired and/or wireless technologies and protocols.

According to various implementations, the display devices 104, 106generally represent functionality for visual output for the clientdevice 102. Additionally, the display devices 104, 106 representfunctionality for receiving various types of input, such as touch input,stylus input, touchless proximity input, and so forth via one or more ofthe touch surfaces 110, 112, which can be used as visual output portionsof the display devices 104, 106. The input module 114 is representativeof functionality to enable the client device 102 to receive input (e.g.,via input mechanisms 124) and to process and route the input in variousways.

The input mechanisms 124 generally represent different functionalitiesfor receiving input to the client device 102, and include a digitizer126, touch input devices 128, and analog input devices 130. Examples ofthe input mechanisms 124 include gesture-sensitive sensors and devices(e.g., such as touch-based sensors), a stylus, a touch pad,accelerometers, a microphone with accompanying voice recognitionsoftware, and so forth. The input mechanisms 124 may be separate orintegral with the display devices 104, 106, with integral examplesincluding gesture-sensitive displays with integrated touch-sensitivesensors.

The digitizer 126 represents functionality for converting various typesof input to the display devices 104, 106, the touch input devices 128,and the analog input devices 130 into digital data that can be used bythe client device 102 in various ways. The analog input devices 130represent hardware mechanisms (e.g., the hinge 108) that are usable togenerate different physical quantities that represent data. Forinstance, the hinge 108 represents a mechanism that can be leveraged togenerate input data by measurement of a physical variable, such as hingeangle of the hinge 108. One or more sensors 132, for example, canmeasure the hinge angle, and the digitizer 126 can convert suchmeasurements into digital data usable by the client device 102 toperform operations to content displayed via the display devices 104,106.

Generally, the sensors 132 represent functionality for detectingdifferent input signals received by the client device 102. For example,the sensors 132 can include one or more hinge sensors configured todetect a hinge angle between the display devices 104, 106. Additionally,the sensors 132 can include grip sensors, such as touch sensors,configured to detect how a user is holding the client device 102. Thesensors 132 can also include motion sensors and/or orientation sensors,such as accelerometers and/or gyroscopes configured to detect physicalmovement and orientation of the display devices 104, 106 in space orrelative movement and orientation with respect to a reference position.In an example, the sensors 132 can include proximity sensors to detect aproximity of the user to one of the display devices 104, 106. Also, thesensors 132 can include audio sensors (e.g., a microphone and/ormicrophone array) to detect audio associated with an audio source (e.g.,the user), such as voice commands issued by the user, and the audio canbe used to determine a relative direction of the user with respect tothe display devices 104, 106 and which of the display devices 104, 106is substantially facing the user. Accordingly, a variety of differentsensors 132 disposed on each of the display devices 104, 106 and can beimplemented to detect various different types of digital and/or analoginput. These and other aspects are discussed in further detail below.

In at least some implementations, the applications 120 include orotherwise make use of an inference module 134 and a verification module136. The inference module 134 and the verification module 136, forexample, are included as part of an application or system software, suchas the operating system 118. Alternatively, the inference module 134 andthe verification module 136 each represent a different standaloneapplication or other functionality.

Generally, the inference module 134 represents functionality forinferring the user's intended primary display, such as by determiningwhich of the display devices 104, 106 the user intends to use as theprimary display. The inference module 134 is configured to utilize inputsignals, such as those detected by the input mechanisms 124 and/or thesensors 132, to determine a posture of the client device 102 based on anorientation and a relative position of the client device 102 relative tothe user, the ground, or another reference location, to make such aninference.

The verification module 136 is configured to utilize various sensorsignals to determine context information associated with the clientdevice 102 in relation to the user and how the user is using the device.In addition, the verification module 136 can use the context informationto verify a gesture being performed and/or to verify the inference madeby the inference module 134. By verifying the gesture being performed,the inference module 134 can avoid inadvertent or unintentional inputbeing recognized as a gesture. In addition, by verifying whether theinference module 134 correctly determined which of the display devices104, 106 the user intended to be the primary display, inference errorscan be identified and corrected. Thus, the user's experience can beimproved over conventional techniques by smoothly transitioning thedisplay to the user's intended primary display without requiring theuser to explicitly select the primary display. Further discussion ofthis and other features is provided below.

Having described an example environment in which the techniquesdescribed herein may operate, consider now a discussion of some exampleimplementation scenarios in accordance with one or more implementations.

Example Implementation Scenarios

This section describes some example implementation scenarios forinference of an intended primary display of a hinged mobile device inaccordance with one or more implementations. The implementationscenarios may be implemented in the environment 100 described above, thesystem 1200 of FIG. 12, and/or any other suitable environment. Theimplementation scenarios and procedures, for example, describe exampleoperations of the client device 102.

FIG. 2 illustrates an example implementation scenario 200 forinteraction between various components of the client device 102 fromFIG. 1. In the illustrated example, the sensors 132 receive a base inputsignal 202. The base input signal 202 can be detected from a variety ofdifferent input mechanisms, such as a touch input (e.g., via a fingerpress or stylus input) to the touch surface 110 or the touch surface 112of the client device 102, a press of a hardware button, a bend in thehinge 108 of the client device 102, a voice command via an audio sensor,or any combination of input mechanisms. In implementations, the baseinput signal 202 can include a device gesture 204 or an implicit gesture206. The device gesture 204 is recognized as a physical movement of atleast one of the display devices 104, 106 of the client device 102. Inimplementations, the physical movement leverages the hinge 108 such thata hinge angle between the display devices 104, 106 is changed. Forexample, the user may open the client device 102 from a closed posture,or further open the client device 102 from an open posture to a flippedposture where the display devices 104, 106 face away from each other inopposite directions. Alternatively, if the client device 102 is in theflipped posture, the user may turn or flip the device over to see theopposite side, which includes a display device that was previouslyfacing away from the user and is now facing toward the user.

The implicit gesture 206 may include physical movement of the clientdevice 102 by the user where the user's goal is not to communicate tothe system that the user now has a particular primary display surface,but rather the user is doing something naturally with the client device102 that can be recognized and detected as a gesture from the system'spoint of view. For instance, the user may lift the client device 102from a stationary location (e.g., on a table, or in a pocket), or turnthe device to cause a display device to face away from the user andtoward another person. From a system point of view, these actions can beconsidered to be gestures for input, even though the user may notexplicitly intend them to be gestures.

The inference module 134 is configured to use the input signal 202detected by the sensors 132 to infer the user's intended primarydisplay. For instance, the inference module 134 is configured todetermine which of the display devices 104, 106 the user intends to beemployed as the primary display. The base input signal 202 can indicatean orientation of the client device 102 in space and a position of eachdisplay device 104, 106 relative to one another.

In addition, the verification module 136 is configured to utilize avariety of context information 208 to verify the input signal 202 wasactually an intentional input rather than an inadvertent or accidentalinput. Further, the verification module 136 is configured to use thecontext information 208 to refine the determination made by theinference module 134 as to which display devices 104, 106 is to be theprimary display. The context information 208 can be determined based ona variety of support signals that can be interpreted as context relatedto the client device 102 and/or the user. This context informationallows the system to better infer which display device the user intendsto use as the primary screen.

The context information 208 can include data or signals associated withone or more of grip 210, relative position 212, sound 214, behavioraldata 216, hall effect 218, user settings 220, calibration data 222,visual data 224, and external connections 226. This is not an exhaustivelist. Rather, these types of context information 208 are described asexamples of the context information 208, and are not to be construed aslimiting. Further, the client device 102 can utilize some or all of thecontext information 208, and can use any subset or combination ofdifferent types of the context information 208.

The grip 210 indicates how the user is grasping or holding the clientdevice 102 during and/or after the input signal 202. For instance, thegrip 210 can be detected by the sensors 132, such as capacitive stripson the outside of the client device 102 or separate capacitive sensorson the rear exterior of the client device 102. Alternatively or inaddition, the grip 210 can be detected based on a capacitance of adisplay surface on the front of the client device 102. The sensors 132can detect whether the user has fingers wrapped around the client device102, which hand (e.g., left or right hand) the user is using to hold theclient device 102, in which of a variety of different device posturesthe user is holding the device, and so on. Accordingly, the grip 210indicates how the user is holding the device, which is usable to inferhow the user intends to use the device.

The relative position 212 refers to a relative position of the clientdevice 102 in relation to the user of the client device 102, in relationto the ground, and/or in relation to another reference location. Forexample, the relative position 212 can indicate whether the clientdevice 102 is resting on a surface or whether a display device is facingthe user. In implementations, the relative position 212 can be used todetermine a current posture of the client device 102. Various types ofsensors 132 can be employed to determine the relative position 212,including cameras, accelerometers, magnetometers, and so on.

The sound 214 can be used to enable a user to initiate commands audibly.For example, one or more audio sensors can be utilized to detect spokencommands by the user and an approximate direction and/or distance of theaudio source (e.g., the user) relative to the client device 102. In thisway, the system can determine which display device 104, 106 is facingthe user.

The behavioral data 216 is representative of how the user tends tointeract with the client device 102 or particular applications executedon the client device 102. For example, when using the client device 102in a posture that allows the user to view both the display devices 104,106 simultaneously, the user may tend to run certain applications on theleft side (e.g., display device 104) and other applications on the rightside (e.g., display device 106). In another example, the user maygenerally take notes on the right side (e.g., display device 106) of theclient device 102 because the user is right-handed, and as a result, theuser's hand does not obscure the other display device (e.g., displaydevice 104).

There are many different reasons why a user may have particularpreferences related to how the user tends to use the client device 102.The behavioral data 216, although it may not explicitly representpreferences in the form of settings, includes behavioral informationabout how the user uses the device. Further, using the behavioral data216, some user actions can be anticipated. For example, when anotetaking application is launched, the system can use the behavioraldata 216 to launch the notetaking application via a particular one ofthe display devices 104, 106 because the system knows the user has apreference for viewing the notetaking application via the particulardisplay device and that the user likely intends that particular displaydevice to be the primary display.

The hall effect 218 refers to the production of a potential differenceacross an electrical conductor when a magnetic field is applied in adirection perpendicular to that of the flow of current. Hall effectsensors (e.g., magnetometer) can detect magnetic fields in closeproximity. In implementations, the hall effect 218 can be used to detectwhen the client device 102 is opened from a closed posture to an openposture and to automatically turn on one or both of the display devices104, 106. Alternatively or additionally, the hall effect 218 can be usedto turn the display devices 104, 106 off when the client device 102 ismanipulated into the closed posture.

The user settings 220 can indicate how the user prefers to use theclient device 102, particularly with respect to ergonomics-related usersettings that are set by the user or by default. Ergonomics-related usersettings can be used to further refine the input signal 202 (e.g.,left/right handedness can be used to predict a likely flip direction, orhand size information can be used for more reliable grip detection). Byusing information associated with the user settings 220, the clientdevice 102 can predict which direction the user is going to turn thedevice when the user's intent is to flip it over. This functionality canbe useful in differentiating situations that are similar in nature, suchas a first situation where the user rotates the device 180 degrees tosee the reverse side, versus a second situation where the user rotatesthe device 180 degrees to show a friend content displayed via theprimary display. In the first situation, the primary display can bechanged to the reverse side to enable the user to view content via thereverse side. In the second situation, however, the user may not desirethe primary display to change but may instead desire the primary displayto temporarily face away from the user in order to show the displayedcontent to the friend, likely with the intent of then turning the deviceback around to continue viewing the original primary display.Accordingly, the user settings 220, alone or in combination with othercontext information 208, can be used to disambiguate similar situations.

The calibration data 222 describes information about the user, such asuser properties that the system is aware of. For example, thecalibration data 222 can include hand dimensions representing the sizeand shape of the user's hand(s) that is grasping the client device 102.The hand dimensions can be used for more reliable grip detection.Further, the hand dimensions can be used to identify the user, theuser's handedness (left or right), a shape of the user's fingers, and soon. This information can allow the system to more robustly detect howthe user is holding the device, which can then be used to infer whichdisplay device is likely intended to be the primary display based on theway the user would predictably perform the device gesture 204 or theimplicit gesture 206.

The visual data 224 refers to information captured via an imagecapturing device, such as a camera of the client device 102. Forexample, the client device can include multiple integrated cameras. Eachdisplay device 104, 106, for instance, can be associated with one ormore cameras, such as front-facing or rear-facing cameras. The camerascan capture images and/or video to detect whether a correspondingdisplay device is facing the user. In implementations, the cameras canbe used to detect whether the user is looking at a particular displaydevice.

The external connections 226 refer to current connections between theclient device 102 and one or more external devices. For example, theclient device 102 can be connected to one or more external displays todisplay content, such as to give a presentation to a group of people. Inthis example, attention is given to the external device rather than theclient device 102. Thus, the external device is likely intended to bethe primary display.

Additional context information 208 can include context corresponding toan application being executed or the operating system 118 itself. Basedon particular occurrences, the system can anticipate that the user islikely going to perform a device gesture 204. For example, with theability to switch between front and rear facing cameras, if the user hasexplicitly selected an in-application command or an operatingsystem-related command that expresses the user's intent of performing anext action, the client device 102 can adjust one or more detectionparameters to more aggressively detect posture changes, device gestures204, and implicit gestures 206, based on a current task and theindication of the next task.

Once the verification module 136 verifies the inferred primary displayor corrects the inferred primary display, a display module 228 providesan output 230 for controlling the display devices 104, 106. For example,the display module 228 is configured to control power to each of thedisplay devices 104, 106, and control which of the display devices 104,106 is to be used as the primary display for output of content. In anexample, the display module 228 is configured to cause an application tobe displayed via a particular display device, change a power state of adisplay device (e.g., place a display device that is not intended to beused as the primary display into a low power state or “off” state, orturn on or wake a display device that is inferred to be the user'sintended primary display), and so on.

In implementations, different sensors 132 can be used in differentimplementations based on which gesture is detected, rather than usingall the sensors 132 all the time. This can reduce power consumption andextend battery life. For instance, when the user flips the client device102 over to view the reverse side, certain sensors (e.g., proximitysensors) can be considered for inferring the user's intended primarydisplay. In contrast, when a different gesture is performed, such as agesture that opens the client device 102, the system can rely less onthe proximity sensors and more on grip sensors. For instance, differentsensor signals can be weighted differently based on different gestures.Accordingly, the client device 102 can determine, during performance ofthe gesture, which gesture is being performed and based on thatdetermination, consider particular sensor signals to refine thatdetermination (e.g., to verify that the determined gesture is in factbeing performed). Conditionally considering signals from various sensors132, rather than simply using all the sensors 132 all the time, reducesrequired processing bandwidth and power consumption, which can lead to alonger battery life.

FIG. 3 depicts example implementation scenarios 300 of devices thatinclude functionality for inference of an intended primary display of ahinged device as described herein. The scenarios 300 include variousdifferent configurations of devices having multiple touch surfaces. Thedevices discussed in the scenarios 300, for instance, representdifferent instances of the client device 102.

For example, in scenario 300 a, multiple display devices 104, 106 arephysically connected to one another and include touch-sensitive displays110, 112, respectively. In implementations, the display devices 104, 106can be connected via a movable connection 302, such as a hinge, a pivot,a joint, a swivel, and so on. The movable connection 302 can allow thedisplay devices 104, 106 to be positioned in a variety of differentpostures, such as a “closed book” posture where the displays 110, 112face each other. Additionally, the display devices 104, 106 can bepositioned in an “open book” posture where the displays 110, 112 arepositioned relative to one another at an angle between zero and 90degrees, or between 90 degrees and 180 degrees. In yet another exampleposition, the displays 110, 112 can be parallel with one another in aside-by-side configuration where both displays 110, 112 face the samedirection. In at least one implementation, the display devices 104, 106can be positioned such that the displays 110, 112 face substantiallyopposite directions, as illustrated in example configuration 304.According to various implementations, touch input to the displays 110,112 can be interpreted according to techniques for inference of anintended primary display of a hinged mobile device described herein.

Scenario 300 b includes a bendable device 308 having a display device310 that is bendable into different configurations, causing at least aportion of the display device 310 to be hidden from the user's view. Forexample, the bendable device 308 can be shaped into a position having afirst portion 310 a of the display device 310 facing the user and asecond portion 310 b of the display device 310 that is non-planar withthe first portion 310 a, such that the second portion 310 b of thedisplay device 310 is essentially “on the backside” of the bendabledevice 308. In at least one implementation, the second portion 310 b canbe positioned normal to the first portion 310 a. Accordingly, a varietyof different positions and configurations of the bendable device 308 arecontemplated, and are not necessarily limited to a front/backconfiguration. According to various implementations, touch input to thefirst portion 310 a and the second portion 310 b can be interpretedaccording to techniques for inference of an intended primary display ofa hinged mobile device described herein.

Scenario 300 c includes a device 312 with a single integrated display314 that can be bent along the hinge 108. The single integrated display314 can include multiple display portions, such as display portion 316and display portion 318, each of which can include touch screenfunctionality. The display portions 316, 318 can be used to displaydifferent content, such as different application user interfaces, or thedisplay portions 316, 318 can be used to display content via a singleapplication user interface across both of the display portions 316, 318.In an example, display portion 318 can be designated as the primarydisplay for presentation of an interactive application (e.g., notetakingapplication) while the other display portion 316 can be used to displaya comparatively-less interactive application, such as a media playerapplication. In another example, both display portions 316, 318 can bedesignated as the primary display, such as for playback of video contentacross both of the display portions 316, 318. Alternatively, a singleapplication user interface displayed across both of the display portions316, 318 can present user interface controls via a designated primarydisplay, which may correspond to the user's handedness, e.g., right/lefthand.

FIG. 4 illustrates example implementation scenarios 400 for postures ofa hinged device in accordance with one or more embodiments. Thescenarios 400 each include an instance of the client device 102 fromFIG. 1 positioned in a particular posture (e.g., position andorientation in space). For example, scenario 400 a represents a “laptop”posture in which the display device 104 is resting on a surface andfacing a direction opposite the surface. For instance, the client device102 may be resting on a table, a desk, a user's lap, or any othersuitable surface. The display device 106 is facing toward a user usingthe client device 102 in a landscape orientation. A hinge angle isformed between the display device 104 and the display device 106, suchas between 60 and 160 degrees. In at least some implementations,although the user may be able to view display device 104, the displaydevice 106 can act as the primary display to display content 402 and thedisplay device 104 can be turned off or placed in a low power state(e.g., sleep, hibernation).

Scenario 400 b represents the client device 102 in a “book” posture, inwhich the client device 102 is held similar to a paper book. In Scenario400 b, the client device 102 is positioned in a portrait orientationwith both display devices 104, 106 being viewable by the user, butoriented toward each other such that the hinge angle formed between thedisplay devices 104, 106 is between 60 degrees and 180 degrees. Here,one or both of the display devices 104, 106 can be designated as theprimary display to display the content 402.

Scenario 400 c includes the client device 102 in a “flat” posture, suchthat display devices 104, 106 face substantially the same direction andthe hinge angle formed between the display devices 104, 106 isapproximately 180 degrees. Here, either one of the display devices 104,106, or both, can be used to display the content 402 and either one ofthe display devices 104, 106 can be designated as the primary display.

Scenario 400 d illustrates the client device 102 in a “flipped” posturein which the display devices 104, 106 are facing opposite directions.The hinge 108 has been bent to “flip” the display device 106 aroundbehind the display device 104. In this scenario 400 d, the displaydevice 104 is viewable by the user, but the display device 106 is notviewable by the user because the display device 106 faces away from theuser. Accordingly, the display device 104 is being used as the primarydisplay. Further, the client device 102 can be held in either a portraitor a landscape orientation to enable the user to view the content 402displayed via the display device 104. In at least some implementations,the display device 106 may be placed in a low power state or turned off.

Alternatively, the user can turn the client device 102 around to viewthe display device 106. Doing so may cause the display device 104 toface away from the user such that the user may no longer be able to viewthe display device 104. In this case, the display device 106 can bedesignated as the primary display to display the content 402, and thedisplay device 104 can be transitioned into the low power state.

Scenario 400 e illustrates a “corner” posture in which the client device102 is placed upright in the portrait orientation with the displaydevices 104, 106 facing outward on different sides of a corner that isformed between the display devices 104, 106. Here, the angle formedbetween the display device 104, 106 may be between 250 degrees and 360degrees to allow different users to view the different display devices104, 106. This posture may be useful when displaying content (e.g., in apresentation) for a small group of people that cannot all view thecontent via a single display device. This posture allows some of thecrowd to move to the side of the client device 102 to view the same ordifferent content on the display device 106. The corner posture isessentially opposite the book posture since the display devices 104, 106face outward rather than inward. In the corner posture, one of thedisplay devices 104, 106 can be designated as the primary display. Forexample, display device 104 can be designated as the primary display todisplay user interface controls for controlling the presentation beingdisplayed via display device 106.

Scenario 400 f represents a “tent” posture in which the client device102 is placed in a landscape orientation with the display devices 104,106 facing outward. Here, the client device 102 is positioned to alloweach of the display devices 104, 106 to be viewed by different users.For example, a first user may view the display device 104 and a seconduser (sitting across from the first user) may view the display device106. Accordingly, the tent posture can allow multi-player applicationsto be played by multiple users on a single device, without allowing theusers to view the other user's screen. Other postures can also allow forsimilar functionality.

In at least one implementation, user interface controls can be treateddifferently on the different display devices. For example, while bothusers have their own view of a multi-player game, a primary display canstill be designated for the primary user. In this example, the displaydevice 104 facing the primary user may include additional controls thatallow the user to control administrative tasks for the game (e.g., save,load, change settings), and the opposing display device 106 may includevarious controls for gameplay but not for the administrative tasks.Accordingly, the primary display can be designated even when bothdisplay devices 104, 106 are used simultaneously for displaying content.

Accordingly, any of a variety of different postures can be utilized todisplay content via a device with multiple display devices connectedtogether by a hinge. Depending on the posture, the display may beadjusted to suit the manner in which the client device 102 is being usedor is intended to be used by the user. Further, a change from oneposture to another posture can trigger a change in the primary display.For example, a change in the hinge angle of the hinge 108 between thedisplay devices 104, 106 can trigger a change in the primary display ifthe change in the hinge angle is greater than a threshold value, e.g.,10 degrees, 15 degrees, 30 degrees, and so on. Any suitable thresholdvalue can be utilized for the change in the hinge angle to trigger achange in the primary display. In implementations, a physicaldisplacement, rather than a hinge angle change, can trigger a change inthe primary display. For example, the physical displacement can includea posture change from the laptop posture in scenario 400 a to the bookposture in the scenario 400 b, where the hinge angle remainssubstantially the same but the orientation of the client device 102 isrotated from a landscape orientation to a portrait orientation. Thetechniques described herein infer the user's intended primary displaybased on physical movement (e.g., physical displacement, change in thehinge angle) of the client device 102 in order to automatically presentthe content to the user in the manner desired by the user.

FIG. 5 depicts an example implementation scenario 500 for inference ofan intended primary display of a hinged mobile device in accordance withone or more embodiments. In scenario 500 a, the client device 102 ispositioned in a flat posture 502 such that both display devices 104, 106are facing the same direction. In this flat posture 502, image 504 isdisplayed across both display devices 104, 106. The user then bends thehinge 108 and physically moves one or both of the display devices 104,106, such as by transitioning the client device 102 from the flatposture 502 to a flipped posture 506. The sensors 132 detect thephysical movement (e.g., displacement) of the display devices 104, 106.Here, the display device 104 is displaced by an amount 508 and thedisplay device 106 is displaced by an amount 510. In implementations,the display device with the least amount of physical displacement incomparison to the other display device can be inferred to be theintended primary display. In the flipped posture 506, the display device104 is facing toward the user but the user can no longer see the displaydevice 106 because the display device 106 is now on the reverse side ofthe client device 102 and facing away from the user. Here, it isdetected that the display device 106 had a greater physical displacementin comparison to the displacement of the display device 104. Based onthis information, the system can infer that the display device 104 isintended to be the primary display since the display device 106 wasmoved to the reverse side of the client device 102. Accordingly, theimage 504 is resized to be displayed via the display device 104 and thedisplay device 106 is turned off or placed in a low power state.

FIG. 6 depicts an example implementation scenario 600 which represents aflip gesture to switch displays in accordance with one or moreembodiments. In the scenario 600, the client device 102 is positioned inthe flipped posture and content 602 is displayed via display device 104while display device 106 is turned off. In order to easily switchdisplays, the user can perform a non-aligned dual-surface gesture, whichcan be referred to as a “coin flip” because it is similar to flipping acoin to view content on the reverse side. For example, non-aligneddual-surface gestures can begin with simultaneous correlated touchpoints on both the touch surface 110 and the touch surface 112, and thencontinue with non-aligned gesture movement on one or both surfaces. Forinstance, in at least one implementation, a user pinches the clientdevice 102 with substantially simultaneous touch inputs 604, 606, andthen moves the touch inputs 604, 606 in opposite directions on eachsurface. For example, gesture movement can include moving the touchinput 604 on the display touch surface 112 to the left while moving thetouch input 606 on the touch surface 110 to the right, as illustrated byarrows 608, 610, respectively. These two gestures can cause the systemto switch the primary display from the display device 106 to the displaydevice 104. Then, if the client device 102 is rotated around alongitudinal axis 612, the content 602 can be viewed via the displaydevice 104. In this way, if the user is using the client device 102 inthe flipped posture and viewing content via display device 106, the usercan easily switch the displays to allow another person to view thecontent via the display device 104 without having to turn the clientdevice 102 over.

FIG. 7 depicts an example implementation scenario 700 for inference ofan intended primary display of a hinged mobile device in accordance withone or more embodiments. In the scenario 700, the client device 102 isbeing used to display the image 504 via both the display devices 104,106 as a single integrated display. Without changing postures of theclient device 102, the user launches a notetaking application 702. Basedon a variety of sensor signals and context information, the system caninfer that the display device 106 is intended by the user to be used asthe primary display for the notetaking application 702.

For example, by detecting the user's left hand 704 grasping the clientdevice 102, the system can identify the user, based on hand size and/orshape, and can determine that the user is right handed based on knownattributes of the user obtained via the user settings 220 or thebehavioral data 216, or both. Alternatively or in addition, because theuser is grasping the client device 102 with the left hand 704, thesystem can infer that the user is intending to write notes with a righthand 706 because generally users do not grasp the client device 102 witha dominant writing hand. In addition to knowing that the user is righthanded, the system can use the behavioral data to determine that theuser has a history of using the notetaking application 702 and/orsimilar types of applications (e.g., based on classification, userinterface controls, functionalities, and/or content of the applications)on the right side via display device 106. This may be because the usercan write with the right hand without obscuring the other display device(display device 104). Accordingly, the client device 102 can utilize avariety of sensors 132 and context information 208 to infer that theuser's intended primary display is the display device 106. Using thisinformation, the client device 102 can then move and resize the displayof the image 504 to display the image 504 only via the display device104 (e.g., left side), and launch the notetaking application 702 via theinferred primary display, e.g., the display device 106 on the rightside.

FIG. 8 depicts an example implementation scenario 800 for inference ofan intended primary display of a hinged mobile device in accordance withone or more embodiments. In the scenario 800, a user 802 is viewing theclient device 102 in the flipped posture, such that the display device106 is facing the user 802 but the display device 104 is facing awayfrom the user 802 and the user 802 cannot see the display device 104. Inthe scenario 700 a, content 804 is displayed for the user via thedisplay device 106. In implementations, the user 802 can turn the devicearound a longitudinal axis 612 of the client device 102 to view theopposite side, e.g., the display device 104 that was previously facingaway from the user 802. When the user 802 turns the device in thismanner, the sensors 132 from FIG. 1 can detect the physical movement ofthe client device 102, and the client device 102 can determine that ithas been turned around. Using context information, such as gripinformation, captured images/video, or proximity signals, the clientdevice 102 can infer that the primary display is intended to switch tothe display device 104, which is the side now facing the user 802.

FIG. 9 depicts an example implementation scenario 900 for inference ofan intended primary display of a hinged mobile device in accordance withone or more embodiments. In the scenario 900 a, the client device 102 isbeing used in the flipped posture and the content 804 is being presentedvia the display device 106, which is facing the user 802. Assume theuser 802 then turns the device around the longitudinal axis 612 to showthe displayed content 804 to another person 902, as illustrated inscenario 900 b. The client device 102 detects the physical movement ofthe client device 102 to infer which display device to use as theprimary display.

In some implementations, the system may incorrectly infer the user'sintended primary display, such as by inferring the primary display to bedisplay device 104, which is now facing the user 802 in scenario 900 b.In this example, however, the user intended the primary display toremain the same when the user turned the device around to allow theother person 902 to view the displayed content 804. To avoid this error,the system can use the context information to determine that the displaydevice 104 is to remain the primary display. This can involveinteraction between the verification module 136 and the inference module134. In an example, the context information obtained by the verificationmodule 136 can include grip information indicating a particular way theuser is grasping the device (e.g., the user's hand is obscuring aportion of the display device 106), visual data detected via a camera904 that indicates the other person 902 facing the display device 106,proximity data indicating that the other person 902 is proximate to thedisplay device 106, and so on. The verification module 136 is configuredto verify whether the inference module 134 likely inferred the primarydisplay correctly, and override the inference if the inferred primarydisplay is determined to likely be incorrect based on the contextinformation. In addition, the verification module 136 is configured to,based on detection of an inference error, update weightings used by theinference module 134 to improve future inferences. Accordingly, thecontext information 208 is used to reduce errors in the inferences madeby the system and more accurately infer the user's intended primarydisplay.

In addition or alternatively, an indication of which display is to bedesignated as the primary display can be provided to the user. In thisway, the user can be informed of whether the client device 102 iscorrectly inferring the intended primary display. In an example, avisual indicator 906 can be displayed via display device 104, or avisual indicator 908 can be displayed via display device 106. Either oneof the visual indicators 906, 908, or both, can be displayed to informthe user of which display device (e.g., display device 104 or displaydevice 106) is to be the primary display. In at least oneimplementation, a light emitting diode (LED) or other light can turn on,flash, or emit a particular color to indicate the primary display.

Further, a user-selectable option to override the determination of whichdisplay device is to be the primary display is provided. Theuser-selectable option (e.g., visual indicator 906) enables the user toeasily override the automated inference of the primary display. In anexample, the user may turn the client device 102 about the longitudinalaxis 612 to view the reverse side. Based on detection of the otherperson 902, the client device 102 infers that the primary display is toremain the display device 106. However, the user 802 can select thevisual indicator 906 to cause the client device 102 to switch theprimary display to the display device 104.

In at least one implementation, if the client device 102 switches theprimary display to the display device 104 when the user turns the clientdevice 102 about the longitudinal axis 612 but the user 802 desires theprimary display to switch instead to the display device 106, the user802 can enter an input, such as a touch input (e.g., tap, double tap,swipe, press and hold) via the touch surface 112 of the display device106. In this example, this touch input overrides the inference andselects the display device 106 as the primary display. Accordingly, avariety of user-selectable options can be provided to allow the user 802to selectively override the determination of which display device is theprimary display. Based on this explicit override input by the user, theverification module 136 can update weightings used by the inferencemodule 134 to improve future inferences.

Having described some example implementation scenarios, consider nowsome example procedures for inference of an intended primary display ofa hinged mobile device in accordance with one or more implementations.

Example Procedures

The following discussion describes example procedures for inference ofan intended primary display of a hinged mobile device in accordance withone or more embodiments. The example procedures may be employed in theenvironment 100 of FIG. 1, the system 1200 of FIG. 12, and/or any othersuitable environment. The procedures, for instance, represent proceduresfor implementing the example implementation scenarios discussed above.In at least some implementations, the steps described for the variousprocedures can be implemented automatically and independent of userinteraction, such as by the inference module 134 and the verificationmodule 136. Further, the steps described below in FIGS. 10 and 11 can beperformed in any suitable combination and/or order, and are not intendedto be construed as limited to the orders described.

FIG. 10 is a flow diagram that describes steps in a method for inferringa user's intended primary display of a hinged mobile device inaccordance with one or more implementations. The method, for instance,describes an example procedure for inferring which of a plurality ofdisplay devices the user intends to use as the primary display.

Step 1000 detects physical movement of one or more of a plurality ofdisplay portions of a computing device. The physical movement isdetected by sensors associated with the computing device, examples ofwhich are described above with respect to FIGS. 1 and 2. In an exampleimplementation, the plurality of display portions includes a firstdisplay portion connected to a second display portion by a hinge. In atleast one implementation, the physical movement is a change in postureof the mobile device, where a hinge angle of a hinge between the displayportions is changed. In some implementations, the physical movement isrotation around an axis, such as a longitudinal axis or a lateral axis.In another example, the physical movement includes displacement inspace, such as a change in altitude. Generally, physical movement mayinclude any one or combination of these or other types of movement.

Step 1002 recognizes the physical movement of the one or more of aplurality of display portions as a base input signal to indicate whichdisplay portion is intended to be used as a primary display. In anexample implementation, the base input signal can indicate anorientation of the client device in space and a position of each displaydevice relative to one another. Examples of the base input signal aredescribed above in relation to FIG. 2.

Step 1004 receives sensor signals providing context information relatedto one or more forms of context associated with the computing device. Inimplementations, the context information indicates various types ofinformation usable to more accurately infer how the user intends to usethe computing device. Examples of the context information are describedabove in relation to FIG. 2.

Step 1006 verifies the base input signal based on the contextinformation. For example, the context information can be used to verifythat the base input signal was not an accidental input, but was anintentional input intended to initiate an operation. An example of thisis described above with respect to scenario 900 of FIG. 9, in which theuser 802 turns the client device 102 around to show displayed content804 to the other person 902. Using the context information thatindicates the way the user is grasping the client device 102 andidentifies the presence of the other person 902, the client device 102can verify that the turning of the client device 102 was not intended tobe an input that switches the primary display.

Step 1008 determines which display portion of the plurality of displayportions to use as the primary display based on the verified base inputsignal. Examples of this step are described above, such as with respectto scenarios 500, 700, 800, and 900 of FIGS. 5 and 7-9, respectively.

Step 1010 initiates the primary display via the determined displayportion. This step can be performed in any suitable way, such as bycausing content to be displayed via a particular display portion.Examples of this step are described above with respect to FIGS. 4-9.Further, in combination with steps 1000-1008, a user-selectable optioncan be provided that is selectable to override the determination of theprimary display, which provides additional control to the user. Anexample of this is described below with respect to FIG. 11.

FIG. 11 is a flow diagram that describes steps in a method for inferringa user's intended primary display of a hinged mobile device inaccordance with one or more implementations. The method, for instance,describes an example procedure for providing an option to override aninference of an intended primary display.

Step 1100 displays content via at least one of a first display portionor a second display portion. The client device 102, for instance,includes two display devices 104, 106 that are connected by a hinge 108.In addition, the first display portion may currently be employed as theprimary display.

Step 1102 recognizes a device gesture based on physical movement of thecomputing device. For example, the client device 102 can determine thatthe posture of the client device 102 has changed to a different posture,such as from an open posture to a flipped posture, as described withrespect to the scenario 500 in FIG. 5.

Step 1104 determines which display portion of the first display portionor the second display portion is to be used as the primary display. Theclient device 102, for example, infers the user's intended primarydisplay based on the device gesture and context information.

Step 1106 provides an indication of which portion is to be designated asthe primary display. For example, the client device 102 can prompt theuser with a visual indication, such as a displayed notification,indicating that the primary display is to be switched, or identifying aparticular display device that is to be designated as the primarydisplay.

Step 1108 provides a user-selectable option to override thedetermination of which display portion is the primary display. Theclient device 102, for example, can display the user-selectable optionvia either or both of the display devices 104, 106 to provide the userthe option of correcting or otherwise overriding the inferred primarydisplay.

Step 1110 overrides the determination of which display portion is theprimary display based on a user input that selects the user-selectableoption. In this way, the user can correct any undesired inferences madeby the system regarding the user's intended primary display, or switchthe primary display after having performed an unintentional devicegesture.

Having described some example procedures for inference of an intendedprimary display of a hinged mobile device, consider now some furtherimplementation details in accordance with one or more implementations.

Implementation Details

Generally, techniques for inference of an intended primary display on ahinged mobile device described herein enable:

-   -   Automatic designation of a primary display on a hinged device    -   Automatic inference of a user's intended primary display based        on physical movement of the hinged device    -   Automatic power conservation by changing a power state of a        non-primary display to a low-power state, based on the inference        of the user's intended primary display    -   An ability to anticipate the user's intended primary display        based on context information    -   More accurate inferences of the user's intended primary display        based on the context information, when compared to conventional        techniques    -   Accurate inferences of the user's intended primary display based        on verification of device gestures and implicit gestures

Accordingly, techniques described herein provide more efficient controlof display devices of a hinged device. Additionally, the techniquesdescribed herein improve the user experience by displaying content onthe most convenient display device. Further, the user experience isimproved by automatically inferring the user's intended primary displaybased on physical movement of the client device or execution of aparticular application. Accordingly, such implementations increaseefficiency and reduce power consumption, thus conserving battery life ofthe client device.

Having described some example implementation details, consider now adiscussion of an example system and device in accordance with one ormore implementations.

Example System and Device

FIG. 12 illustrates an example system generally at 1200 that includes anexample computing device 1202 that is representative of one or morecomputing systems and/or devices that may implement the varioustechniques described herein. In at least some implementations, thecomputing device 1202 represents an implementation of the client device102 discussed above. The computing device 1202 may, for example, beconfigured to assume a mobile configuration through use of a housingformed and sized to be grasped and carried by one or more hands of auser, illustrated examples of which include a mobile phone, mobile gameand music device, and tablet computer although other examples are alsocontemplated. In at least some implementations, the client device 102may be implemented as a wearable device, such as a smart watch, smartglasses, a dual-surface gesture-input peripheral for a computing device,and so forth.

The example computing device 1202 as illustrated includes a processingsystem 1204, one or more computer-readable media 1206, and one or moreI/O interface 1208 that are communicatively coupled, one to another.Although not shown, the computing device 1202 may further include asystem bus or other data and command transfer system that couples thevarious components, one to another. A system bus can include any one orcombination of different bus structures, such as a memory bus or memorycontroller, a peripheral bus, a universal serial bus, and/or a processoror local bus that utilizes any of a variety of bus architectures. Avariety of other examples are also contemplated, such as control anddata lines.

The processing system 1204 is representative of functionality to performone or more operations using hardware. Accordingly, the processingsystem 1204 is illustrated as including hardware element 1210 that maybe configured as processors, functional blocks, and so forth. This mayinclude implementation in hardware as an application specific integratedcircuit or other logic device formed using one or more semiconductors.The hardware elements 1210 are not limited by the materials from whichthey are formed or the processing mechanisms employed therein. Forexample, processors may be comprised of semiconductor(s) and/ortransistors (e.g., electronic integrated circuits (ICs)). In such acontext, processor-executable instructions may beelectronically-executable instructions.

The computer-readable storage media 1206 is illustrated as includingmemory/storage 1212. The memory/storage 1212 represents memory/storagecapacity associated with one or more computer-readable media. Thememory/storage component 1212 may include volatile media (such as randomaccess memory (RAM)) and/or nonvolatile media (such as read only memory(ROM), Flash memory, optical disks, magnetic disks, and so forth). Thememory/storage component 1212 may include fixed media (e.g., RAM, ROM, afixed hard drive, and so on) as well as removable media (e.g., Flashmemory, a removable hard drive, an optical disc, and so forth). Thecomputer-readable media 1206 may be configured in a variety of otherways as further described below.

Input/output interface(s) 1208 are representative of functionality toallow a user to enter commands and information to computing device 1202,and also allow information to be presented to the user and/or othercomponents or devices using various input/output devices. Examples ofinput devices include a keyboard, a cursor control device (e.g., amouse), a microphone, a scanner, touch functionality (e.g., capacitiveor other sensors that are configured to detect physical touch), a camera(e.g., which may employ visible or non-visible wavelengths such asinfrared frequencies to recognize movement as gestures that do notinvolve touch), and so forth. Examples of output devices include adisplay device (e.g., a monitor or projector), speakers, a printer, anetwork card, tactile-response device, and so forth. Thus, the computingdevice 1202 may be configured in a variety of ways to support userinteraction.

The computing device 1202 is further illustrated as beingcommunicatively and physically coupled to an input device 1214 that isphysically and communicatively removable from the computing device 1202.In this way, a variety of different input devices may be coupled to thecomputing device 1202 having a wide variety of configurations to supporta wide variety of functionality. In this example, the input device 1214includes one or more keys 1216, which may be configured as pressuresensitive keys, mechanically switched keys, and so forth.

The input device 1214 is further illustrated as include one or moremodules 1218 that may be configured to support a variety offunctionality. The one or more modules 1218, for instance, may beconfigured to process analog and/or digital signals received from thekeys 1216 to determine whether a keystroke was intended, determinewhether an input is indicative of resting pressure, supportauthentication of the input device 1214 for operation with the computingdevice 1202, and so on.

Various techniques may be described herein in the general context ofsoftware, hardware elements, or program modules. Generally, such modulesinclude routines, programs, objects, elements, components, datastructures, and so forth that perform particular tasks or implementparticular abstract data types. The terms “module,” “functionality,” and“component” as used herein generally represent software, firmware,hardware, or a combination thereof. The features of the techniquesdescribed herein are platform-independent, meaning that the techniquesmay be implemented on a variety of commercial computing platforms havinga variety of processors.

An implementation of the described modules and techniques may be storedon or transmitted across some form of computer-readable media. Thecomputer-readable media may include a variety of media that may beaccessed by the computing device 1202. By way of example, and notlimitation, computer-readable media may include “computer-readablestorage media” and “computer-readable signal media.”

“Computer-readable storage media” may refer to media and/or devices thatenable persistent storage of information in contrast to mere signaltransmission, carrier waves, or signals per se. Thus, computer-readablestorage media refers to non-signal bearing media and does not includesignals per se. The computer-readable storage media includes hardwaresuch as volatile and non-volatile, removable and non-removable mediaand/or storage devices implemented in a method or technology suitablefor storage of information such as computer readable instructions, datastructures, program modules, logic elements/circuits, or other data.Examples of computer-readable storage media may include, but are notlimited to, RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, harddisks, magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, or other storage device, tangible media, orarticle of manufacture suitable to store the desired information andwhich may be accessed by a computer.

“Computer-readable signal media” may refer to a signal-bearing mediumthat is configured to transmit instructions to the hardware of thecomputing device 1202, such as via a network. Signal media typically mayembody computer readable instructions, data structures, program modules,or other data in a modulated data signal, such as carrier waves, datasignals, or other transport mechanism. Signal media also include anyinformation delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media include wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared, and other wireless media.

As previously described, hardware elements 1210 and computer-readablemedia 1206 are representative of modules, programmable device logicand/or fixed device logic implemented in a hardware form that may beemployed in some implementations to implement at least some aspects ofthe techniques described herein, such as to perform one or moreinstructions. Hardware may include components of an integrated circuitor on-chip system, an application-specific integrated circuit (ASIC), afield-programmable gate array (FPGA), a complex programmable logicdevice (CPLD), and other implementations in silicon or other hardware.In this context, hardware may operate as a processing device thatperforms program tasks defined by instructions and/or logic embodied bythe hardware as well as a hardware utilized to store instructions forexecution, e.g., the computer-readable storage media describedpreviously.

Combinations of the foregoing may also be employed to implement varioustechniques described herein. Accordingly, software, hardware, orexecutable modules may be implemented as one or more instructions and/orlogic embodied on some form of computer-readable storage media and/or byone or more hardware elements 1210. The computing device 1202 may beconfigured to implement particular instructions and/or functionscorresponding to the software and/or hardware modules. Accordingly,implementation of a module that is executable by the computing device1202 as software may be achieved at least partially in hardware, e.g.,through use of computer-readable storage media and/or hardware elements1210 of the processing system 1204. The instructions and/or functionsmay be executable/operable by one or more articles of manufacture (forexample, one or more computing devices 1202 and/or processing systems1204) to implement techniques, modules, and examples described herein.

In the discussions herein, various different embodiments are described.It is to be appreciated and understood that each embodiment describedherein can be used on its own or in connection with one or more otherembodiments described herein. Further aspects of the techniquesdiscussed herein relate to one or more of the following embodiments.

A system to infer an intended primary display of a computing device withmultiple displays based on movement of the computing device, the systemcomprising: a device having a plurality of display portions physicallyconnected to each other by a hinge; a plurality of sensors disposed oneach of the plurality of display portions; at least one processor; andat least one computer-readable storage media storing instructions thatare executable by the at least one processor to perform operationsincluding: detecting, by sensors associated with the computing device,physical movement of at least one display portion of a plurality ofdisplay portions, the plurality of display portions including a firstdisplay portion connected to a second display portion by a hinge;recognizing the physical movement as an input signal to indicate whichof the plurality of display portions is intended to be used as a primarydisplay; determining that the first display portion is likely intendedto be used as the primary display based on the input signal; andinitiate the primary display via the first display portion.

In addition to any of the above described systems, any one orcombination of: wherein said determining includes detecting a greaterphysical displacement of the second display portion in comparison to aphysical displacement of the first display portion; wherein the firstdisplay portion and the second display portion are facing oppositedirections, prior to the detecting, the second display portion is facinga user of the computing device and is currently used as the primarydisplay, and the physical movement includes flipping the computingdevice over to cause the first display portion to face the user; whereinthe first display portion and the second display portion are facingopposite directions, prior to the detecting, the first display portionis facing a user of the computing device and is currently used as theprimary display, and the physical movement includes turning thecomputing device to cause the first display portion to face anotheruser; wherein the physical movement includes transitioning the computingdevice from a closed posture to an open posture; wherein the physicalmovement includes transitioning the computing device from one of aclosed posture or an open posture to a flipped posture in which thefirst display portion and the second display portion are facing awayfrom each other in opposite directions; wherein the physical movementincludes a hinge angle of the hinge being changed by an amount greaterthan a threshold value; wherein the physical movement includes thecomputing device being lifted from a stationary location; and whereinthe sensors are disposed on each display device of the plurality ofdisplay devices, and the sensors include at least one of motion sensorsor orientation sensors.

A method implemented by a computing device for inferring an intendedprimary display of multiple displays based on movement of the computingdevice, the method comprising: recognizing physical movement of one ormore of a plurality of display portions as a device gesture to indicatewhich display portion is intended to be used as a primary display;receiving, from the plurality of sensors, sensor signals providingcontext information related to one or more forms of context associatedwith the computing device; verifying the device gesture based on thecontext information; determining which display portion of the pluralityof display portions to use as the primary display based on the verifieddevice gesture; and initiating the primary display via the determineddisplay portion.

In addition to any of the above described methods, any one orcombination of: wherein the physical movement transitions the computingdevice from a first posture to a second posture; wherein the physicalmovement changes an orientation of the computing device from a firstorientation to a second orientation; wherein the plurality of sensorsinclude grip sensors that detect which hand a user is using to grasp thecomputing device; and wherein the sensors include at least one of acamera, proximity sensors, hall effect sensors, magnetometers,microphones, or grip sensors.

A method implemented by a computing device for inferring an intendedprimary display of multiple displays based on movement of the computingdevice, the method comprising: displaying content via at least one of afirst display portion or a second display portion, the first displayportion connected to the second display portion via a hinge, the firstdisplay portion being used as a primary display; recognizing a devicegesture based on physical movement of the computing device; determiningwhich display portion of the first display portion or the second displayportion is to be used as the primary display; providing an indication ofwhich portion is to be designated as the primary display; and providinga user-selectable option to override the determination of which displayportion is the primary display.

In addition to any of the above described methods, any one orcombination of: wherein providing the indication includes providing avisual indication via the primary display; further comprising overridingthe determination of which display portion is the primary display basedon a user input that selects the user-selectable option; wherein thedevice gesture includes turning the computing device around effective tocause the first display portion to face away from user of the computingdevice, and the determining includes determining that the first displayportion is to continue being used as the primary display; wherein thedevice gesture includes turning the computing device around effective tocause the first display portion to face away from user of the computingdevice, and the determining includes determining that the second displayportion is to be used as the primary display; and wherein thedetermining includes detecting an amount of physical displacement ofeach of the first display portion and the second display portion, andthe determining is based on a least amount of physical displacementbetween the first display portion and the second display portion.

CONCLUSION

Techniques for inference of an intended primary display of a hingedmobile device are described. Although implementations are described inlanguage specific to structural features and/or methodological acts, itis to be understood that the implementations defined in the appendedclaims are not necessarily limited to the specific features or actsdescribed. Rather, the specific features and acts are disclosed asexample forms of implementing the claimed implementations.

What is claimed is:
 1. A system comprising: a device having a pluralityof display portions physically connected to each other by a hinge; aplurality of sensors disposed on each of the plurality of displayportions; at least one processor; and at least one computer-readablestorage media storing instructions that are executable by the at leastone processor to perform operations including: detecting, by sensorsassociated with the computing device, physical movement of at least onedisplay portion of a plurality of display portions, the plurality ofdisplay portions including a first display portion connected to a seconddisplay portion by a hinge; recognizing the physical movement as aninput signal to indicate which of the plurality of display portions isintended to be used as a primary display; determining that the firstdisplay portion is likely intended to be used as the primary displaybased on the input signal; and initiate the primary display via thefirst display portion.
 2. A system as described in claim 1, wherein saiddetermining includes detecting a greater physical displacement of thesecond display portion in comparison to a physical displacement of thefirst display portion.
 3. A system as described in claim 1, wherein: thefirst display portion and the second display portion are facing oppositedirections; prior to the detecting, the second display portion is facinga user of the computing device and is currently used as the primarydisplay; and the physical movement includes flipping the computingdevice over to cause the first display portion to face the user.
 4. Asystem as described in claim 1, wherein: the first display portion andthe second display portion are facing opposite directions; prior to thedetecting, the first display portion is facing a user of the computingdevice and is currently used as the primary display; and the physicalmovement includes turning the computing device to cause the firstdisplay portion to face another user.
 5. A system as described in claim1, wherein the physical movement includes transitioning the computingdevice from a closed posture to an open posture.
 6. A system asdescribed in claim 1, wherein the physical movement includestransitioning the computing device from one of a closed posture or anopen posture to a flipped posture in which the first display portion andthe second display portion are facing away from each other in oppositedirections.
 7. A system as described in claim 1, wherein the physicalmovement includes a hinge angle of the hinge being changed by an amountgreater than a threshold value.
 8. A system as described in claim 1,wherein the physical movement includes the computing device being liftedfrom a stationary location.
 9. A system as described in claim 1,wherein: the sensors are disposed on each display device of theplurality of display devices; and the sensors include at least one ofmotion sensors or orientation sensors.
 10. A method implemented by acomputing device, the method comprising: recognizing physical movementof one or more of a plurality of display portions as a device gesture toindicate which display portion is intended to be used as a primarydisplay; receiving, from the plurality of sensors, sensor signalsproviding context information related to one or more forms of contextassociated with the computing device; verifying the device gesture basedon the context information; determining which display portion of theplurality of display portions to use as the primary display based on theverified device gesture; and initiating the primary display via thedetermined display portion.
 11. A method as described in claim 10,wherein the physical movement transitions the computing device from afirst posture to a second posture.
 12. A method as described in claim10, wherein the physical movement changes an orientation of thecomputing device from a first orientation to a second orientation.
 13. Amethod as described in claim 10, wherein the plurality of sensorsinclude grip sensors that detect which hand a user is using to grasp thecomputing device.
 14. A method as described in claim 10, wherein thesensors include at least one of a camera, proximity sensors, hall effectsensors, magnetometers, microphones, or grip sensors.
 15. A methodimplemented by a computing device, the method comprising: displayingcontent via at least one of a first display portion or a second displayportion, the first display portion connected to the second displayportion via a hinge, the first display portion being used as a primarydisplay; recognizing a device gesture based on physical movement of thecomputing device; determining which display portion of the first displayportion or the second display portion is to be used as the primarydisplay; providing an indication of which portion is to be designated asthe primary display; and providing a user-selectable option to overridethe determination of which display portion is the primary display.
 16. Amethod as described in claim 15, wherein providing the indicationincludes providing a visual indication via the primary display.
 17. Amethod as described in claim 15, further comprising overriding thedetermination of which display portion is the primary display based on auser input that selects the user-selectable option.
 18. A method asdescribed in claim 15, wherein: the device gesture includes turning thecomputing device around effective to cause the first display portion toface away from user of the computing device; and the determiningincludes determining that the first display portion is to continue beingused as the primary display.
 19. A method as described in claim 15,wherein: the device gesture includes turning the computing device aroundeffective to cause the first display portion to face away from user ofthe computing device; and the determining includes determining that thesecond display portion is to be used as the primary display.
 20. Amethod as described in claim 15, wherein: the determining includesdetecting an amount of physical displacement of each of the firstdisplay portion and the second display portion; and the determining isbased on a least amount of physical displacement between the firstdisplay portion and the second display portion.